Navigation peek ahead and behind

ABSTRACT

Some embodiments of the invention provide a navigation application that allows a user to peek ahead or behind during a turn-by-turn navigation presentation that the application provides while tracking a device (e.g., a mobile device, a vehicle, etc.) traversal of a physical route. As the device traverses along the physical route, the navigation application generates a navigation presentation that shows a representation of the device on a map traversing along a virtual route that represents the physical route on the map. While providing the navigation presentation, the navigation application can receive user input to look ahead or behind along the virtual route. Based on the user input, the navigation application moves the navigation presentation to show locations on the virtual route that are ahead or behind the displayed current location of the device on the virtual route. This movement can cause the device representation to no longer be visible in the navigation presentation. Also, the virtual route often includes several turns, and the peek ahead or behind movement of the navigation presentation passes the presentation through one or more of these turns. In some embodiments, the map can be defined presented as a two-dimensional (2D) or a three-dimensional (3D) scene.

INCORPORATION BY REFERENCE; DISCLAIMER

Each of the following applications are hereby incorporated by reference:application Ser. No. 15/462,593 filed on Mar. 17, 2017; application Ser.No. 14/292,609 filed on May 30, 2014. The Applicant hereby rescinds anydisclaimer of claim scope in the parent application(s) or theprosecution history thereof and advises the USPTO that the claims inthis application may be broader than any claim in the parentapplication(s).

BACKGROUND

Many map-based applications available today are designed for a varietyof different devices (e.g., desktops, laptops, tablet devices,smartphones, handheld global positioning system (GPS) receivers, etc.)and for various different purposes (e.g., navigation, browsing, sports,etc.). Most of these applications generate displays of a map based onmap data that describes relative locations of streets, highways, pointsof interest, etc., in the map. Some map-based applications provide anavigation feature, which provides the user with turn-by-turninstructions to a destination. Most of these applications, however, donot have sophisticated features that today's demanding users wish tohave in their map-based applications.

BRIEF SUMMARY

Some embodiments of the invention provide a navigation application thatallows a user to peek ahead or behind during a turn-by-turn navigationpresentation that the application provides while tracking a device(e.g., a mobile device, a vehicle, etc.) traversal of a physical route.As the device traverses along the physical route, the navigationapplication generates a navigation presentation that shows arepresentation of the device on a map traversing along a virtual routethat represents the physical route on the map. While providing thenavigation presentation, the navigation application can receive userinput to look ahead or behind along the virtual route. Based on the userinput, the navigation application changes the navigation presentation toshow locations on the virtual route that are ahead or behind thedisplayed current location of the device on the virtual route. Thischange can cause the device representation to no longer be visible inthe navigation presentation. Also, the virtual route often includesseveral turns, and the peek ahead or behind movement of the navigationpresentation can pass the presentation through one or more of theseturns. In some embodiments, the map can be presented as atwo-dimensional (2D) or a three-dimensional (3D) scene.

In some embodiments, the device has a touch-sensitive display screenthrough which it can receive touch input for moving the navigationpresentation along the virtual route. In some of these embodiments, thenavigation application computes a first distance based on the receivedtouch input. Based on the computed first distance, the navigationapplication computes a second distance to move the navigationpresentation along the route. In some embodiments, the second computeddistance is directly proportional to the first computed distance. Inother embodiments, the second distance is not directly proportional tothe first computed distance. For instance, some embodiments compute thesecond distance based on a formulation that reduces gradually increasesto the second distance as the first distance increases.

After moving the navigation presentation ahead or behind the currentposition, the navigation application in some embodiments returns thenavigation presentation to the displayed current location in the mapthat corresponds to the current location of the device along thephysical route. For instance, in some embodiments, the navigationapplication returns the navigation presentation to the current locationwhen the device reaches a location along the physical route at which thedevice has to perform a navigation maneuver. Conjunctively, oralternatively, the navigation application in some embodiments returnsthe navigation presentation to the current location based on theexpiration of a timer that the application set after the touch inputterminated. Alternatively, the navigation application in someembodiments returns the navigation presentation to the current locationonce the touch input terminates.

In some embodiments, the application generates the navigationpresentation from a perspective of a virtual camera that traverses alonga virtual route on a map as the device traverses along the physicalroute. As the virtual camera traverses along the virtual route, itdefines for rendering successive scenes of the map that correspond tosuccessive positions of the device along the physical route. Based onthe user input, the navigation application moves the virtual cameraalong the virtual route to generate renderings of the map at locationsahead or behind on the virtual route. In some cases, the virtual routeincludes several turns, and the movement of the virtual camera takes thevirtual camera past one or more of these turns.

As mentioned above, the map in some embodiments can be presented as atwo-dimensional (2D) or a three-dimensional (3D) scene. When the map isviewed as a 2D scene, the virtual camera captures successive top-downviews of the 2D map scene in some embodiments. On the other hand, whenthe map is viewed as a 3D scene, the virtual camera captures successiveperspective views of the 3D map scene in some embodiments. In someembodiments, the navigation application changes an angle of rotation ofthe virtual camera so that the perspective view generated by the virtualcamera includes more of the 3D map scene that is ahead along the route.Some embodiments change the virtual camera's angle of rotation beforemoving of the virtual camera, while other embodiments change the virtualcamera's angle of rotation while moving of the virtual camera.

The preceding Summary is intended to serve as a brief introduction tosome embodiments of the invention. It is not meant to be an introductionor overview of all inventive subject matter disclosed in this document.The Detailed Description that follows and the Drawings that are referredto in the Detailed Description will further describe the embodimentsdescribed in the Summary as well as other embodiments. Accordingly, tounderstand all the embodiments described by this document, a full reviewof the Summary, Detailed Description and the Drawings is needed.Moreover, the claimed subject matters are not to be limited by theillustrative details in the Summary, Detailed Description and theDrawings, but rather are to be defined by the appended claims, becausethe claimed subject matters can be embodied in other specific formswithout departing from the spirit of the subject matters.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the invention are set forth in the appendedclaims. However, for purposes of explanation, several embodiments of theinvention are set forth in the following figures.

FIG. 1 illustrates an example of a navigation application that allows auser to peek ahead along a navigated route.

FIG. 2 illustrates the same example as described in FIG. 1, except inthe example illustrated in FIG. 2, the navigation application changesthe maneuver banners in each stage to show the next upcoming maneuverfor virtual route position that is being displayed by the navigationpresentation.

FIG. 3 illustrates an example where the navigation application returnsthe virtual camera to the device's current location after the expirationof a timer that the application sets once a peek-ahead swipe gestureterminates.

FIG. 4 presents an example that illustrates the navigation applicationreturning the navigation presentation to the current location when thedevice nears a location for a navigation maneuver.

FIG. 5 presents an example that illustrates the navigation applicationrotating the virtual camera upwards before moving the virtual camera inresponse to a swipe gesture to peek ahead.

FIG. 6 illustrates an example of the navigation application performing apeek behind operation to present a portion of the navigated route thathas already been traversed.

FIG. 7 illustrates a process that the navigation application of someembodiments performs to present a navigation presentation that can peekahead or peek behind a navigated route.

FIG. 8 illustrates example architecture of a navigation application thatallows the user to peek ahead and behind a route.

FIG. 9 is an example of an architecture of a mobile computing device ofsome embodiments.

FIG. 10 conceptually illustrates an example of an electronic system withwhich some embodiments of the invention are implemented.

FIG. 11 illustrates a map service operating environment of someembodiments.

DETAILED DESCRIPTION

In the following detailed description of the invention, numerousdetails, examples, and embodiments of the invention are set forth anddescribed. However, it will be clear and apparent to one skilled in theart that the invention is not limited to the embodiments set forth andthat the invention may be practiced without some of the specific detailsand examples discussed.

Some embodiments of the invention provide a navigation application thatallows a user to peek ahead or behind during a turn-by-turn navigationpresentation that the application provides while tracking a device(e.g., a mobile device, a vehicle, etc.) traversal of a physical route.To provide navigation instructions between a starting location and adestination location, the navigation application identifies a physicalroute between the two locations and generates a navigation presentationthat shows a representation of the device on a map traversing along adisplayed virtual route that represents the physical route.

As the device reaches junctures along the physical route at which thedevice has to perform a maneuver, the navigation presentation providesvisual and/or audible instructions regarding the maneuver that thedevice has to perform. To provide such instructions and presentation,the navigation application uses one or more location services (e.g.,global positioning system (GPS) service) of the device to track thecurrent position of the device and correlate the tracked position to aposition on the navigated route. During turn-by-turn navigation, thenavigation application in some embodiments (1) detects when the devicehas traveled off route, (2) identifies another route to the destination,and (3) displays new route and instructions to the destination based onthe newly identified route.

While providing the navigation presentation, the navigation applicationcan receive user input to look ahead or behind along the virtual route.Based on the user input, the navigation application changes thenavigation presentation to show locations on the virtual route that areahead or behind the displayed current location of the device on thevirtual route. This change can cause the device representation to nolonger be visible in the navigation presentation. Also, the virtualroute often includes several turns, and the peck ahead or behindmovement of the navigation presentation can pass the presentationthrough one or more of these turns. In some embodiments, the map can bepresented as a two-dimensional (2D) or a three-dimensional (3D) scene.

In some embodiments, the device has a touch-sensitive display screen.For instance, in some embodiments, the device has a multi-touchinterface for allowing a user to provide touch and gestural inputsthrough the screen to interact with the application. Examples of suchdevices are smartphones (e.g., iPhone

sold by Apple Inc., phones operating the Android

operating system, phones operating the Windows

operating system, etc.), tablet computers (e.g., iPads

sold by Apple Inc., tablets operating the Android

operating system, tablets operating the Windows

operating system, etc.), laptop computers, desktop computers, etc.

Through the touch interface, the navigation application can receivetouch input for moving the navigation presentation along the virtualroute. In some of these embodiments, the navigation application computesa first distance based on the received touch input. Based on thecomputed first distance, the navigation application computes a seconddistance to move the navigation presentation along the route. In someembodiments, the second computed distance is directly proportional tothe first computed distance. In other embodiments, the second distanceis not directly proportional to the first computed distance. Forinstance, some embodiments compute the second distance based on aformulation that reduces gradually increases to the second distance asthe first distance increases.

After moving the navigation presentation ahead or behind the currentposition, the navigation application in some embodiments returns thenavigation presentation to the displayed current location in the mapthat corresponds to the current location of the device along thephysical route. For instance, in some embodiments, the navigationapplication returns the navigation presentation to the current locationwhen the device reaches a location along the physical route at which thedevice has to perform a navigation maneuver. Conjunctively, oralternatively, the navigation application in some embodiments returnsthe navigation presentation to the current location based on theexpiration of a timer that the application set after the touch inputterminated. Alternatively, the navigation application in someembodiments returns the navigation presentation to the current locationonce the touch input terminates.

In some embodiments, the application generates the navigationpresentation from a perspective of a virtual camera that traverses alonga virtual route on a map as the device traverses along the physicalroute. In some embodiments, the virtual camera traverses along thevirtual route based on the travel direction and speed of the devicetraveling along the physical route. In some embodiments, the directionand speed of the device are captured by and derived from directionaldata (e.g., GPS data, triangulated cell-tower data, etc.) associatedwith the device.

As the virtual camera traverses along the virtual route, it defines forrendering successive scenes of the map that correspond to successivepositions of the device along the physical route. Based on the userinput, the navigation application moves the virtual camera along thevirtual route to generate renderings of the map at locations ahead orbehind on the virtual route. In some cases, the virtual route includesseveral turns, and the movement of the virtual camera takes the virtualcamera past one or more of these turns.

As mentioned above, the map in some embodiments can be presented as atwo-dimensional (2D) or a three-dimensional (3D) scene. When the map isviewed as a 2D scene, the virtual camera captures successive top-downviews of the 2D map scene in some embodiments. On the other hand, whenthe map is viewed as a 3D scene, the virtual camera captures successiveperspective views of the 3D map scene in some embodiments. In someembodiments, the navigation application allows a user to change theperspective rendering position of the virtual camera so that the virtualcamera can capture the 3D navigation scene from a variety of differentperspectives (e.g., from a variety of different positions andorientations).

In some embodiments, the navigation application changes an angle ofrotation of the virtual camera so that the perspective view generated bythe virtual camera includes more of the 3D map scene that is ahead alongthe route. Some embodiments change the virtual camera's angle ofrotation before moving of the virtual camera, while other embodimentschange the virtual camera's angle of rotation while moving of thevirtual camera.

Several more detailed embodiments of the invention will now be describedby reference to FIGS. 1-6. In these embodiments, the navigationpresentation is a driving navigation presentation that shows the devicetraversing along a road network. However, in some embodiments, the peekahead feature and/or peek behind feature are provided in walkingnavigation presentations or other navigation presentations that show thedevice traversing along walking or other pathways. Thus, one of ordinaryskill should understand that the embodiments described below are equallyapplicable to all types of navigation presentations, such as drivingnavigation presentations, walking navigation presentations, bikingnavigation presentations, etc. Examples of other walking navigationpresentations are described in U.S. patent application Ser. No.14/055,847.

FIG. 1 illustrates an example of a navigation application that allows auser to peek ahead along a navigated route. In this example, thenavigation application executes on a device (e.g., a mobile device, avehicle's electronic information system, etc.) that has atouch-sensitive display screen for receiving touch inputs (e.g., singletouch or multi-touch inputs) and/or gestural inputs through the screento interact with the application. In some embodiments, the navigationapplication is a standalone application, while in other embodiments itis part of another application, e.g., is part of an integrated mappingapplication that includes several modalities, such as location browsing,map searching, route inspection and route navigating operations.

To provide its navigation operations, the navigation application usesone or more location services of the device and one or more local orremote route generating services. Specifically, the navigationapplication of different embodiments obtains a route between twolocations differently. In some embodiments, the navigation applicationcomputes the route locally on the device, while in other embodiments,the navigation application sends the information about the starting andending locations to a remote server, which computes the route andreturns the computed route back to the navigation application. Thenavigation application uses one or more location services of the deviceto track the current position of the device and correlate the trackedposition to a position on the navigated route. For instance, in someembodiments, the navigation application uses GPS coordinates receivedthrough the device's GPS receiver.

The example presented FIG. 1 is illustrated in terms of threeoperational stages 105, 110, and 115 of the user interface (UI) of thenavigation application. Each stage has two sides, a left side showing anavigation presentation output of the navigation application and a rightside showing the manner by which the navigation application generatesthat stage's navigation presentation output. As shown by the right sideof each of the stages, the navigation application uses a virtual camera150 that captures a 3D map scene 190 to produce the navigationpresentation.

Specifically, to present turn-by-turn navigation instructions, thenavigation application of FIG. 1 tracks the device's traversal of aphysical route and provides a navigation presentation from a perspectiveof the virtual camera 150 that traverses along a virtual route 125 on amap 190 as the device traverses along the physical route between twolocations in the physical world. As the virtual camera traverses alongthe virtual route, it specifies for rendering successive scenes of themap that correspond to successive positions of the device along thephysical route, as further described below.

While providing the navigation presentation, the navigation applicationcan receive user input to look ahead or behind along the virtual route.Based on the user input, the navigation application moves the virtualcamera along the virtual route to generate renderings of the map atlocations ahead or behind on the virtual route. In some cases, thevirtual route includes several turns, and the movement of the virtualcamera takes the virtual camera past one or more of these turns.

The left-side of the three stages 105, 110 and 115 shows the navigationapplication changing the navigation presentation in response to atwo-finger swipe gesture. The first stage 105 shows the navigationpresentation at the start of the two-finger swipe gesture. At thisstage, the navigation application displays a navigation presentationthat includes (1) the current position of the device with the puck 120,(2) the virtual route 125 that lays ahead of the puck to represent thephysical route that the device still has to navigate to the destination,(3) a 3D map view 130 (e.g., buildings, streets, etc.) that is about thevirtual route, and (4) a banner 135 that overlays the 3D map view toprovide text instruction 137 and graphical instruction 139 regarding anupcoming navigation maneuver. Although the swipe-down gesture is shownin FIG. 1 to direct the application to perform the peek ahead operation,other input (e.g., the swipe-up gesture) in other embodiments initiatesthe peek ahead operation.

The navigation application uses a 3D affordance 140 to transition thenavigation presentation between a 3D presentation and a 2D presentation.This affordance changes its appearance (e.g., changes its shading) tosignify whether the navigation presentation is in 2D or 3D. When the mapis viewed as a 2D scene, the virtual camera 150 captures successivetop-down views of the map scene 130. On the other hand, when the map isviewed as a 3D scene, the virtual camera captures successive perspectiveviews of the 3D map scene in some embodiments. The right side of thefirst stage 105 shows the perspective view that the virtual cameracaptures to produce the navigation presentation that is provided on theleft side of this stage. As mentioned above, this perspective view andits associated navigation presentation are defined to be about thecurrent location of the device.

The second stage 110 shows the navigation presentation after it hasmoved in response to the swipe gesture of the first stage 105. Thesecond stage 110 shows the presentation after it has moved along thevirtual route 125 past the puck 120, which represents the currentlocation of the device. Specifically, the left side of the second stage110 shows the navigation presentation after it moves past the currentposition of the device on Union street, turns right on B street andapproaches a left turn on 1^(st) street. The right side of the secondstage 110 shows the virtual camera 150 after it has moved along thevirtual route from Union Street and onto B street on the 3D map scene190. The virtual camera's perspective view of the 3D map scene 190 inthe second stage is used to produce the 3D map view 132 of thenavigation presentation that is shown on the left side of this stage.

The second stage 110 shows the continuation of the swipe gesture.Accordingly, the third stage 115 shows the navigation presentation afterit has turned left turn on 1^(st) street and is approaching a roundabout ahead. The right side of the second stage 110 shows the virtualcamera 150 after it has moved along the virtual route from B street onto1^(st) street on the 3D map scene 190. The virtual camera's perspectiveview of the 3D map scene 190 in the third stage is used to produce the3D map view 134 of the navigation presentation that is shown on the leftside of this stage.

In some embodiments, the navigation application computes the distance tomove the virtual camera in response to a swipe gesture based on thelength of the swipe gesture on the display screen of the device. Forinstance, in some embodiments, the navigation application computes afirst distance based on the received swipe input. Based on the computedfirst distance, the navigation application computes a second distance tomove the virtual camera along the route. In some embodiments, the secondcomputed distance is directly proportional to the first computeddistance. In other embodiments, the second distance is not directlyproportional to the first computed distance. For instance, someembodiments compute the second distance based on a formulation thatreduces gradually increases to the second distance as the first distanceincreases.

In some embodiments, the navigation application presents a new maneuverbanner 135 for the next upcoming maneuver as the device travels along anavigated route, in order to present text and graphical informationabout the upcoming maneuver in the new maneuver banner. As shown in theexample illustrated in FIG. 1, the navigation application in someembodiments does not change the maneuver banner 135 as it changes thenavigation presentation to allow a user to peek ahead along the route.

In other embodiments, however, the navigation application does changethe maneuver banner 135 as it moves the navigation presentation inresponse to user input to peek ahead along the route. FIG. 2 illustratesthe same example as described in FIG. 1, except in the exampleillustrated in FIG. 2, the navigation application changes the maneuverbanners in each stage to show the next upcoming maneuver for virtualroute position that is being displayed by the navigation presentation.Accordingly, the banner 135 in first stage 205 shows information aboutthe upcoming right turn on B street, the banner 240 in second stage 210shows information about the upcoming left turn on 1^(st) street, and thebanner 245 in the third stage 215 shows information about the maneuverat an upcoming turnabout.

In some embodiments, the navigation application returns the virtualcamera to a current location in the map that is defined by a currentlocation of the device along the physical route, after moving thevirtual camera in response to user input to peek ahead or behind along avirtual route that is being traversed in the navigation presentationprovided by the navigation application.

For instance, the navigation application in some embodiments returns thevirtual camera to the current location based on expiration of a timerthat the application set after the touch input that moved the virtualcamera terminated. One such example is illustrated in FIG. 3. In thisexample, the virtual camera returns to the current location of thedevice 30 second after the touch input terminated. This example isillustrated in terms of five operational stages 305-325 of thenavigation application UI. The first three stages 305, 310, and 315 ofthis figure are identical to the three stages 105, 110, and 115 of FIG.1, except now the navigation application sets a timer 330 upon thetermination of the swipe gesture at the end of the third stage 315.

The fourth stage 320 shows the navigation application still presentingthe navigation presentation at the peek ahead position that was reachedat the time of the third stage 315. This is the case even though 25seconds have elapsed on the timer, and the device has traveled 250 feettowards the juncture with B street, at which point it needs to make aright turn onto this street. The traveled distance can be deduced fromthe change in the distance information that the banner 135 specifiesbetween the third and fourth stages 315 and 320, while the 25 secondscan be deduced from the rotation of the seconds hand 350 of the timer330. The fifth stage 325 shows that after 30 seconds, the navigationapplication returns the navigation presentation to show the currentlocation of the device. In this example, the current location of thedevice after the 30 seconds is 225 feet from the intersection of Unionand B street.

Instead of setting a timer and waiting for it to count up to aparticular time value, some embodiments set the timer to a particularvalue, and then have the timer count down to another value (e.g., to 0).Also, instead of setting a timer and waiting for the timer to expire,the navigation application in some embodiments immediately returns thenavigation presentation to the current location of the device when theswipe gesture ends (i.e., when the user terminates the two-finger touchof the display screen). Alternatively, in some embodiments, thenavigation application returns the navigation presentation to thecurrent location because the current location corresponds to a locationnear which the device has to perform a navigation maneuver along thephysical route.

FIG. 4 presents an example that illustrates the navigation applicationreturning the navigation presentation to the current location when thedevice nears a location for a navigation maneuver. This example isillustrated in terms of five operational stages 405-425 of thenavigation application UI. The first three stages 405-415 of thisexample are similar to the first three stages 305-315 of the example ofFIG. 3. However, in the third stage 415, the navigation application doesnot set a timer once the swipe gesture ends.

In the fourth stage 420, the navigation presentation remains at the peekahead position that was reached at the time of the third stage. In thisstage, the device is within 125 feet of the intersection of Union and Bstreet, where it has to perform a maneuver. The fifth stage 425 showsthat once the device is within 100 feet of this maneuver, the navigationapplication returns the navigation presentation to the current locationof the device because the device will soon have to perform a maneuveralong the navigated route to stay on the route.

In some embodiments, the navigation application changes an angle ofrotation of the virtual camera so that the perspective view generated bythe virtual camera includes more of the 3D map scene that is ahead alongthe route. Some embodiments change the virtual camera's angle ofrotation before moving of the virtual camera, while other embodimentschange the virtual camera's angle of rotation while moving of thevirtual camera.

FIG. 5 presents an example that illustrates the navigation applicationrotating the virtual camera upwards before moving the virtual camera inresponse to a swipe gesture to peek ahead. This example is illustratedin terms of three operational stages 505-515 of the navigationapplication UI. The first stage 505 is identical to the first stage 105of FIG. 1, in that it shows the start of a two-finger swipe gesture topeek ahead while the navigation application is providing a navigationpresentation.

The second stage 510 illustrates that upon detecting the peek-aheadswipe gesture, the navigation application rotates the virtual cameraupwards and in a direction away from the 3D map scene 190. Thenavigation application rotates the virtual camera upwards so that theperspective view captured by the virtual camera can include more of the3D map scene 190 that is ahead along the route.

In rotating the virtual camera upwards, the navigation application inthis example maintains the location of the virtual camera fixed. Inother words, the application in this example does not begin to move thevirtual camera along the route before it finishes moving the virtualcamera upward. Also, while rotating the camera, the application does notmove the virtual camera along an arc 520, which is an arc along whichthe virtual camera moves in some embodiments to transition from atop-down 2D view of the map to one or more 3D perspective views of themap. Movement of the virtual camera along such an arc is described inU.S. Published Patent Applications 2013/0321401, 2013/0321400, and2013/0322702, which are incorporated here by reference. In otherembodiments, however, the navigation application begins to move thevirtual camera along the route and/or along the arc 520 (e.g., upwardsalong this arc), while rotating the virtual camera upwards away from the3D map scene at the beginning of the peek ahead movement.

The third stage 515 shows that after rotating the virtual camera upwardsin the second stage 510, the navigation application moves the virtualcamera along the virtual route in response to the peek-ahead swipeinput.

FIGS. 1-5 show examples in which the navigation application peeks aheadalong a navigated route in response to user input. FIG. 6, on the otherhand, illustrates an example of the navigation application performing apeek behind operation to present a portion of the navigated route thathas already been traversed. This example is illustrates in three stages605-615.

This example is similar to the example illustrated in FIG. 1, exceptthat instead of receiving a swipe-down gesture, the device in FIG. 6receives a swipe up gesture. The three stages 605-615 illustrate that inresponse to the swipe up gesture, the virtual camera travels back alongthe virtual route. In traveling back along the virtual route, thevirtual camera (1) goes back over a left turn that the device made goingfrom Main street onto Union street, and (2) continues backward on Mainstreet along the path of the virtual route. The second and third stages610 and 615 show that as the camera travels back along the route, thenavigation presentation 632 and 634 in these stages updates to reflectprior positions of the device along the route. Although the swipe-upgesture is shown in FIG. 6 to direct the application to perform the peekbehind operation, other input (e.g., the swipe-down gesture) in otherembodiments initiates the peek behind operation.

FIG. 7 illustrates a process 700 that the navigation application of someembodiments performs to present a navigation presentation that can peekahead or peek behind a navigated route. This process starts whenever auser directs the navigation application to start a navigationpresentation that provides turn-by-turn navigation instructions as theuser travels from a starting location to a destination location.

At 705, the process displays a navigation presentation based on thecurrent location of the device. As the device traverses along thephysical route, the navigation presentation shows a representation ofthe device on a map traversing along a virtual route that represents thephysical route on the map. As the device reaches junctures along thephysical route at which the device has to perform a maneuver, thenavigation presentation provides visual and/or audible instructionsregarding the maneuver that the device has to perform. To provide suchinstructions and presentation, the navigation application uses one ormore location services (e.g., GPS service) of the device to track thecurrent position of the device and correlate the tracked position to aposition on the navigated route.

After 710, the process determines whether the navigation application hasreceived input that directs the application to peek ahead or behind thedevice's current location in the navigation presentation. If not, theprocess determines (at 740) whether it should end. The process decidesthat it should end in some embodiments, when the device reaches itsdestination or when the user manually ends the navigation presentation.When the process determines (at 740) that it should end, it ends.Otherwise, it returns to 705, to present the navigation presentation forthe current location of the device along the navigated route.

When the process determines (at 710) that the application has receivedinput to peek ahead or behind, the process computes (at 715) a distanceto move the camera based on the user's input. In some embodiments, thedevice has a touch-sensitive display screen through which it can receivetouch input for moving the navigation presentation along the virtualroute. In some of these embodiments, the process 700 computes (at 715) afirst distance based on the received touch input. Based on the computedfirst distance, the process 700 computes (at 715) a second distance tomove the navigation presentation along the route. In some embodiments,the second computed distance is directly proportional to the firstcomputed distance.

In other embodiments, the second distance is not directly proportionalto the first computed distance. For instance, as further describedbelow, the process 700 iterates through 715 several times during theperiod that the user provides one touch input to peek ahead or behindthe current location of the navigated presentation. In each iteration,the process 700 of some embodiments (1) computes a first distance thatcorresponds to an incremental portion of the touch input, and (2) fromthe computed first distance for that iteration, computes the seconddistance based on a formulation that reduces the computed seconddistance in subsequent iterations for the same computed first distance.This approach is meant to make it harder to peek ahead or behind atfarther distances ahead or behind the current location on the navigatedroute.

After computing the distance to move the camera, the process (at 720)moves the camera along the navigated route by the computed distance, andrenders the navigation presentations from the new position of thecamera. In some cases, the virtual route includes several turns, and themovement of the virtual camera takes the virtual camera past one or moreof these turns, so that the device's representation is no longer visiblein the navigation presentation. Also, before moving the camera forwardto peek ahead the navigated route, the process 700 in some embodimentsrotates (at 720) the virtual camera slightly upward so that theperspective view generated by the virtual camera includes more of the 3Dmap scene that is ahead along the route. Other embodiments change thevirtual camera's angle of rotation gradually while moving of the virtualcamera in response to user input.

After 720, the process determines (at 725) whether the user input thatinitiated the peek ahead or behind operation has terminated. If not, theprocess determines (at 730) whether it should return the navigationpresentation to the current location of the device. If not, the processreturns to 715 to compute another incremental first distance inputvalue, so that it can compute an incremental second distance value tomove the camera and then move the camera based on the incremental seconddistance value. When the process determines (at 730) that it shouldreturn to navigation presentation to the current location of the device,it returns to 705 to display the navigation presentation based on thecurrent location of the device.

The process makes the determination at 730 because in some embodimentsthe peek ahead or behind operation can be overridden by other factors.For instance, even while the user maintains his touch input for peekingahead or behind, the process 700 in some embodiments returns thenavigation presentation to the current location of the device when thedevice approaches a maneuver along a juncture. Other embodiments,however, do not override the peek ahead or behind request of the userwhile the user is maintaining his touch input. Accordingly, theseembodiments transition from 725 to 715 when the process determines (at715) that the user input has not terminated.

When the process determines (at 725) that the user input that initiatedthe peek ahead or behind operate has terminated, it transitions to 735,where it stays until it determines that the navigation presentationshould return to the current location of the device. In differentembodiments, the process 700 returns the navigation presentation to thecurrent location of the device for different reasons. For instance, insome embodiments, the process 700 returns the navigation presentation tothe current location when the device reaches a location along thephysical route at which the device has to perform a navigation maneuver.Conjunctively, or alternatively, the process 700 in some embodimentsreturns the navigation presentation to the current location based on theexpiration of a timer that the application set after the touch inputterminated. Alternatively, the process 700 in some embodiments returnsthe navigation presentation to the current location once the touch inputterminates.

When the process determines (at 735) that the navigation presentation tothe current location of the device, the process returns to 705 todisplay the navigation presentation based on the current location of thedevice.

FIG. 8 illustrates example architecture of a navigation application thatallows the user to peek ahead and behind a route. In this example, anavigation application 800 of some embodiments executes on the operatingsystem 805 of a mobile device. As shown, the navigation application 800includes a touch interface 810, a GUI manager 815, a virtual cameramanager 820, a rendering module 825, a route manager 830, and a routegenerator 835. This figure also illustrates a map server 840 and a routeserver 845.

The device 805 of some embodiments has a touch-sensitive screen (notshown) and/or a near-touch sensitive screen (not shown) that displaysthe output of the navigation application 800. The device 805 alsofacilitates the interaction between the navigation application and themap server 840 and the route server 845. In this figure, the device'sown hardware and software architecture is not depicted for thesimplicity of description and illustration. More details about a deviceon which the navigation application may execute will be describedfurther below by reference to FIG. 9.

The map server 840 is a remote server that provides map data to thenavigation application 800 that describes relative locations of streets,highways, points of interest, etc., in the map per the navigationapplication 800's request. The map data contains 2D and 3D map data atdifferent zoom levels and perspectives.

The route server 845 is a remote server that provides route data to thenavigation application 800 upon request. In some embodiments, thenavigation application 800 sends information about a starting locationand a destination location to the router server 845. The route server845 of some embodiments computes a set of routes for different modes oftransportation and returns the routes to the navigation application 800.

The route manager 830 of the navigation application receives informationabout starting and destination locations and sends the information tothe router server 845 or to the route generator 835 to obtain routesthat includes sets of navigation instructions. In some embodiments, theroute manager 830 receives the information from the user through the GUImanager 815, which receives user selection/or specification through GUIitems that the GUI manager 815 manages. The route manager 830 of someembodiments uses one or both of the route generator 835 and the routeserver 845 to obtain the routes. The router manager 830 of someembodiments also makes the default selection of a route and keeps trackof the default mode of transportation.

The route generator 835 generates routes based on the information aboutthe starting and ending locations from the route manager. The routegenerator 835 is a local equivalent of the route server 845. The routegenerator 835 is part of the navigation application 800 in someembodiments. In some embodiments, however, the route generator 835 is astand-alone application that executes on the device 805.

The touch interface 810 receives the user's interaction with the screen(not shown) of the device 805. In some embodiments, the touch interface810 receives touch information (e.g., coordinates of the part of thescreen that sensed a touch). The touch interface 810 analyzes theinformation and determines whether the information can be interpretedmeaningful gestures such vertical/horizontal swipes, whether there hasbeen a multi-touch, etc. During a turn-by-turn navigation presentation,the touch interface 810 sends the analysis of the touch information tothe virtual camera manager 820.

Based on the touch input, the virtual camera manager 820 translates theamount of touch input into a movement of the virtual camera. Thismovement of virtual camera includes instructions for rotating and/ormoving the camera. The virtual camera manager 820 sends theseinstructions to the rendering module so that the rendering module canrender a new location in the 2D or 3D scene that is being rendered toproduce the turn-by-turn navigation presentation. In identifying the newlocation to render, the virtual camera or the rendering engine maintainsthe view to be rendered along the navigated route. In other words, thepeek ahead or behind distance that is computed based on the gesturalinput is used in some embodiments to move the camera ahead or behind thenavigated route to render positions ahead or behind the current locationon the navigated route.

The GUI manager 815 manages a set of GUI items. When the virtual cameramanager 820 determines that the virtual camera has to move past one ormore junctures along the route, GUI manager receives input from thevirtual camera manager that causes the GUI manager to change themaneuver banners that it displays over the map in the navigationpresentation. This input is different in different embodiments. It mightbe the identities of the passed junctures in some embodiments, while itis simply a distance along the navigated route in other embodiments.Also, as mentioned above, the maneuver banners are not updated in someembodiments as the virtual camera peeks ahead or behind the navigatedroute. Accordingly, in these embodiments, the virtual camera does notdirect the GUI manager to update the maneuver banners.

The GUI manager 815 also interacts with the route manager 830. Asmentioned above, the GUI manager 815 provides the route manager with theuser-specified information about routes to generate. The GUI manager 815also requests and receives navigation instructions and generatesrendering instructions for drawing banners in the display area. The GUIpasses the rendering instructions to the rendering module 825 so thatthe rendering module 825 renders the banner in the display area. The GUImanager 815 generates rendering instructions for drawing other GUI items(e.g., an end control, a list control, route selection banners, etc.) inthe display area. The GUI manager 815 also generates renderinginstructions based on the user's interaction with the GUI items.

The rendering module 825 receives rendering instructions from the GUImanager 815, the virtual camera manager 820, and/or the route manager830. The rendering module 825 also obtains map data from the map server840. The rendering module 825 draws map views, routes, GUI items, etc.according to the instructions and map data.

Many of the above-described features and applications are implemented assoftware processes that are specified as a set of instructions recordedon a computer readable storage medium (also referred to as computerreadable medium). When these instructions are executed by one or morecomputational or processing unit(s) (e.g., one or more processors, coresof processors, or other processing units), they cause the processingunit(s) to perform the actions indicated in the instructions. Examplesof computer readable media include, but are not limited to, CD-ROMs,flash drives, random access memory (RAM) chips, hard drives, erasableprogrammable read-only memories (EPROMs), electrically erasableprogrammable read-only memories (EEPROMs), etc. The computer readablemedia does not include carrier waves and electronic signals passingwirelessly or over wired connections.

In this specification, the term “software” is meant to include firmwareresiding in read-only memory or applications stored in magnetic storagewhich can be read into memory for processing by a processor. Also, insome embodiments, multiple software inventions can be implemented assub-parts of a larger program while remaining distinct softwareinventions. In some embodiments, multiple software inventions can alsobe implemented as separate programs. Finally, any combination ofseparate programs that together implement a software invention describedhere is within the scope of the invention. In some embodiments, thesoftware programs, when installed to operate on one or more electronicsystems, define one or more specific machine implementations thatexecute and perform the operations of the software programs.

The applications of some embodiments operate on mobile devices, such assmart phones (e.g., iPhones

and tablets (e.g., iPads

). FIG. 9 is an example of an architecture 900 of such a mobilecomputing device. Examples of mobile computing devices includesmartphones, tablets, laptops, etc. As shown, the mobile computingdevice 900 includes one or more processing units 905, a memory interface910 and a peripherals interface 915.

The peripherals interface 915 is coupled to various sensors andsubsystems, including a camera subsystem 920, a wireless communicationsubsystem(s) 925, an audio subsystem 930, an I/O subsystem 935, etc. Theperipherals interface 915 enables communication between the processingunits 905 and various peripherals. For example, an orientation sensor945 (e.g., a gyroscope) and an acceleration sensor 950 (e.g., anaccelerometer) is coupled to the peripherals interface 915 to facilitateorientation and acceleration functions.

The camera subsystem 920 is coupled to one or more optical sensors 940(e.g., a charged coupled device (CCD) optical sensor, a complementarymetal-oxide-semiconductor (CMOS) optical sensor, etc.). The camerasubsystem 920 coupled with the optical sensors 940 facilitates camerafunctions, such as image and/or video data capturing. The wirelesscommunication subsystem 925 serves to facilitate communicationfunctions. In some embodiments, the wireless communication subsystem 925includes radio frequency receivers and transmitters, and opticalreceivers and transmitters (not shown in FIG. 9). These receivers andtransmitters of some embodiments are implemented to operate over one ormore communication networks such as a GSM network, a Wi-Fi network, aBluetooth network, etc. The audio subsystem 930 is coupled to a speakerto output audio (e.g., to output voice navigation instructions).Additionally, the audio subsystem 930 is coupled to a microphone tofacilitate voice-enabled functions, such as voice recognition (e.g., forsearching), digital recording, etc.

The I/O subsystem 935 involves the transfer between input/outputperipheral devices, such as a display, a touch screen, etc., and thedata bus of the processing units 905 through the peripherals interface915. The I/O subsystem 935 includes a touch-screen controller 955 andother input controllers 960 to facilitate the transfer betweeninput/output peripheral devices and the data bus of the processing units905. As shown, the touch-screen controller 955 is coupled to a touchscreen 965. The touch-screen controller 955 detects contact and movementon the touch screen 965 using any of multiple touch sensitivitytechnologies. The other input controllers 960 are coupled to otherinput/control devices, such as one or more buttons. Some embodimentsinclude a near-touch sensitive screen and a corresponding controllerthat can detect near-touch interactions instead of or in addition totouch interactions.

The memory interface 910 is coupled to memory 970. In some embodiments,the memory 970 includes volatile memory (e.g., high-speed random accessmemory), non-volatile memory (e.g., flash memory), a combination ofvolatile and non-volatile memory, and/or any other type of memory. Asillustrated in FIG. 9, the memory 970 stores an operating system (OS)972. The OS 972 includes instructions for handling basic system servicesand for performing hardware dependent tasks.

The memory 970 also includes communication instructions 974 tofacilitate communicating with one or more additional devices; graphicaluser interface instructions 976 to facilitate graphic user interfaceprocessing; image processing instructions 978 to facilitateimage-related processing and functions; input processing instructions980 to facilitate input-related (e.g., touch input) processes andfunctions; audio processing instructions 982 to facilitate audio-relatedprocesses and functions; and camera instructions 984 to facilitatecamera-related processes and functions. The instructions described aboveare merely exemplary and the memory 970 includes additional and/or otherinstructions in some embodiments. For instance, the memory for asmartphone may include phone instructions to facilitate phone-relatedprocesses and functions. The above-identified instructions need not beimplemented as separate software programs or modules. Various functionsof the mobile computing device can be implemented in hardware and/or insoftware, including in one or more signal processing and/or applicationspecific integrated circuits.

While the components illustrated in FIG. 9 are shown as separatecomponents, one of ordinary skill in the art will recognize that two ormore components may be integrated into one or more integrated circuits.In addition, two or more components may be coupled together by one ormore communication buses or signal lines. Also, while many of thefunctions have been described as being performed by one component, oneof ordinary skill in the art will realize that the functions describedwith respect to FIG. 9 may be split into two or more integratedcircuits.

FIG. 10 conceptually illustrates another example of an electronic system1000 with which some embodiments of the invention are implemented. Theelectronic system 1000 may be a computer (e.g., a desktop computer,personal computer, tablet computer, etc.), phone, PDA, or any other sortof electronic or computing device. Such an electronic system includesvarious types of computer readable media and interfaces for variousother types of computer readable media. Electronic system 1000 includesa bus 1005, processing unit(s) 1010, a graphics processing unit (GPU)1015, a system memory 1020, a network 1025, a read-only memory 1030, apermanent storage device 1035, input devices 1040, and output devices1045.

The bus 1005 collectively represents all system, peripheral, and chipsetbuses that communicatively connect the numerous internal devices of theelectronic system 1000. For instance, the bus 1005 communicativelyconnects the processing unit(s) 1010 with the read-only memory 1030, theGPU 1015, the system memory 1020, and the permanent storage device 1035.

From these various memory units, the processing unit(s) 1010 retrievesinstructions to execute and data to process in order to execute theprocesses of the invention. The processing unit(s) may be a singleprocessor or a multi-core processor in different embodiments. Someinstructions are passed to and executed by the GPU 1015. The GPU 1015can offload various computations or complement the image processingprovided by the processing unit(s) 1010. In some embodiments, suchfunctionality can be provided using CoreImage's kernel shading language.

The read-only-memory (ROM) 1030 stores static data and instructions thatare needed by the processing unit(s) 1010 and other modules of theelectronic system. The permanent storage device 1035, on the other hand,is a read-and-write memory device. This device is a non-volatile memoryunit that stores instructions and data even when the electronic system1000 is off. Some embodiments of the invention use a mass-storage device(such as a magnetic or optical disk and its corresponding disk drive,integrated flash memory) as the permanent storage device 1035.

Other embodiments use a removable storage device (such as a floppy disk,flash memory device, etc., and its corresponding drive) as the permanentstorage device. Like the permanent storage device 1035, the systemmemory 1020 is a read-and-write memory device. However, unlike storagedevice 1035, the system memory 1020 is a volatile read-and-write memory,such a random access memory. The system memory 1020 stores some of theinstructions and data that the processor needs at runtime. In someembodiments, the invention's processes are stored in the system memory1020, the permanent storage device 1035, and/or the read-only memory1030. For example, the various memory units include instructions forprocessing multimedia clips in accordance with some embodiments. Fromthese various memory units, the processing unit(s) 1010 retrievesinstructions to execute and data to process in order to execute theprocesses of some embodiments.

The bus 1005 also connects to the input and output devices 1040 and1045. The input devices 1040 enable the user to communicate informationand select commands to the electronic system. The input devices 1040include alphanumeric keyboards and pointing devices (also called “cursorcontrol devices”), cameras (e.g., webcams), microphones or similardevices for receiving voice commands, etc. The output devices 1045display images generated by the electronic system or otherwise outputdata. The output devices 1045 include printers and display devices, suchas cathode ray tubes (CRT) or liquid crystal displays (LCD), as well asspeakers or similar audio output devices. Some embodiments includedevices such as a touchscreen that function as both input and outputdevices.

Finally, as shown in FIG. 10, bus 1005 also couples electronic system1000 to a network 1025 through a network adapter (not shown). In thismanner, the computer can be a part of a network of computers (such as alocal area network (“LAN”), a wide area network (“WAN”), or anIntranet), or a network of networks, such as the Internet. Any or allcomponents of electronic system 1000 may be used in conjunction with theinvention.

Some embodiments include electronic components, such as microprocessors,storage and memory that store computer program instructions in amachine-readable or computer-readable medium (alternatively referred toas computer-readable storage media, machine-readable media, ormachine-readable storage media). Some examples of such computer-readablemedia include RAM, ROM, read-only compact discs (CD-ROM), recordablecompact discs (CD-R), rewritable compact discs (CD-RW), read-onlydigital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a varietyof recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.),flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.),magnetic and/or solid state hard drives, read-only and recordableBlu-Ray

discs, ultra density optical discs, any other optical or magnetic media,and floppy disks. The computer-readable media may store a computerprogram that is executable by at least one processing unit and includessets of instructions for performing various operations. Examples ofcomputer programs or computer code include machine code, such as isproduced by a compiler, and files including higher-level code that areexecuted by a computer, an electronic component, or a microprocessorusing an interpreter.

While the above discussion primarily refers to microprocessor ormulti-core processors that execute software, some embodiments areperformed by one or more integrated circuits, such as applicationspecific integrated circuits (ASICs) or field programmable gate arrays(FPGAs). In some embodiments, such integrated circuits executeinstructions that are stored on the circuit itself. In addition, someembodiments execute software stored in programmable logic devices(PLDs), ROM, or RAM devices.

As used in this specification and any claims of this application, theterms “computer”, “server”, “processor”, and “memory” all refer toelectronic or other technological devices. These terms exclude people orgroups of people. For the purposes of the specification, the termsdisplay or displaying means displaying on an electronic device. As usedin this specification and any claims of this application, the terms“computer readable medium,” “computer readable media,” and “machinereadable medium” are entirely restricted to tangible, physical objectsthat store information in a form that is readable by a computer. Theseterms exclude any wireless signals, wired download signals, and anyother ephemeral signals.

Various embodiments may operate within a map service operatingenvironment.

FIG. 11 illustrates one possible embodiment of an operating environment1100 for a map service (also referred to as a mapping service) 1130 andclient devices 1102 a-1102 c. In some embodiments, devices 1102 a, 1102b, and 1102 c communicate over one or more wired or wireless networks1110. For example, wireless network 1110, such as a cellular network,can communicate with a wide area network (WAN) 1120, such as theInternet, by use of gateway 1114. A gateway 1114 in some embodimentsprovides a packet oriented mobile data service, such as General PacketRadio Service (GPRS), or other mobile data service allowing wirelessnetworks to transmit data to other networks, such as wide area network1120. Likewise, access device 1112 (e.g., IEEE 802.11g wireless accessdevice) provides communication access to WAN 1120.

The client devices 1102 a and 1102 b can be any portable electronic orcomputing device capable of communicating with a map service (e.g.,smart phone, tablet, laptop computer, etc.). Device 1102 c can be anynon-portable electronic or computing device capable of communicatingwith a map service (e.g., desktop computer, etc.). These devices may bemultifunction devices capable of various functions (e.g., placing phonecalls, sending electronic messages, producing documents, etc.). Thoughthe devices 1102 a-1102 c are not shown as each accessing the mapservice 1130 via either the wireless network 1110 and gateway 1114 orthe access device 1112, one of ordinary skill in the art will recognizethat the client devices of some embodiments may access the map servicevia multiple different wired and/or wireless protocols.

Devices 1102 a-1102 c can also establish communications by other means.For example, these devices may communicate with other wireless devices(e.g., other devices 1102 b, cell phones, etc.) over the wirelessnetwork 1110 or through access device 1112. Likewise the devices 1102a-1102 c can establish peer-to-peer communications 1140 (e.g., apersonal area network) by use of one or more communication subsystems,such as Bluetooth

communication or similar peer-to-peer protocols.

Devices 1102 a-1102 c may also receive Global Positioning Satellite(GPS) signals from GPS satellites 1160. In addition, in some embodimentsthe map service 1130 and other services 1150 may also receive GPSsignals from GPS satellites 1160.

A map service 1130 may provide map services for one or more clientdevices 1102 a-1102 c in communication with the map service 1130 throughvarious communication methods and protocols. A map service 1130 in someembodiments provides map information (e.g., map tiles used by the clientdevices to generate a two-dimensional or three-dimensional mappresentation) and other map-related data, such as two-dimensional mapimage data (e.g., aerial view of roads utilizing satellite imagery),three-dimensional map image data (e.g., traversable map withthree-dimensional features, such as buildings), route and directioncalculations (e.g., driving route data, ferry route calculations,directions between two points for a pedestrian, etc.), real-timenavigation data (e.g., turn-by-turn visual navigation data in two orthree dimensions), traffic data, location data (e.g., where the clientdevice currently is located), and other geographic data (e.g., wirelessnetwork coverage, weather, traffic information, or nearbypoints-of-interest). In various embodiments, the map service data mayinclude localized labels for different countries or regions. Localizedlabels may be utilized to present map labels (e.g., street names, citynames, points of interest) in different languages on client devices. Theclient devices 1102 a-1102 c may utilize these map services to obtainthe various map service data, then implement various techniques toprocess the data and provide the processed data to various entities(e.g., internal software or hardware modules, display screens of theclient devices, external display screens, or other external systems ordevices.

The map service 1130 of some embodiments provides map services bygenerating and distributing the various types of map service data listedabove, including map information used by the client device to generateand display a map presentation. In some embodiments, the map informationincludes one or more map tiles. The map tiles may include raster imagedata (e.g., bmp, gif, jpg/jpeg/, png, tiff, etc. data) for display as amap presentation. In some embodiments, the map tiles providevector-based map data, with the map presentation data encoded usingvector graphics (e.g., svg or drw data). The map tiles may also includevarious other information pertaining to the map, such as metadata. Someembodiments also encode style data (e.g., used to generate textures)into the map tiles. The client device processes (e.g., renders) thevector and/or raster image data to generate a map presentation fordisplay as a two-dimensional or three-dimensional map presentation. Totransmit the map tiles to a client device 1102 a-1102 c, the map service1130 of some embodiments, performs various optimization techniques toanalyze a map tile before encoding the tile.

In some embodiments, the map tiles are generated by the map service 1130for different possible display resolutions at the client devices 1102a-1102 c. In some embodiments, the higher zoom levels may include moredetail (e.g., more street level information, etc.). On the other hand,map tiles for lower zoom levels may omit certain data (e.g., the streetlevel details would not be used when displaying the entire earth).

To generate the map information (e.g., map tiles), the map service 1130may obtain map service data from internal or external sources. Forexample, satellite imagery used in map image data may be obtained fromexternal services, or internal systems, storage devices, or nodes. Otherexamples may include, but are not limited to, GPS assistance servers,wireless network coverage databases, business or personal directories,weather data, government information (e.g., construction updates or roadname changes), or traffic reports. Some embodiments of a map service mayupdate map service data (e.g., wireless network coverage) for analyzingfuture requests from client devices.

In some embodiments, the map service 1130 responds to requests from theclient devices 1102 a-1102 c for map information. The client devices mayrequest specific portions of a map, or specific map tiles (e.g.,specific tiles at specific zoom levels). In some embodiments, the clientdevices may provide the map service with starting locations (or currentlocations) and destination locations for a route calculations, andrequest turn-by-turn navigation data. A client device may also requestmap service rendering information, such as map textures or style sheets.Requests for other geographic data may include, but are not limited to,current location, wireless network coverage, weather, trafficinformation, or nearby points-of-interest.

The client devices 1102 a-1102 c that obtain map service data from themap service 1130 and render the data to display the map information intwo-dimensional and/or three-dimensional views. Some embodiments displaya rendered map and allow a user, system, or device to provide input tomanipulate a virtual camera for the map, changing the map displayaccording to the virtual camera's position, orientation, andfield-of-view. Various forms and input devices are implemented tomanipulate a virtual camera. In some embodiments, touch input, throughcertain single or combination gestures (e.g., touch-and-hold or a swipe)manipulate the virtual camera. Other embodiments allow manipulation ofthe device's physical location to manipulate a virtual camera. Otherinput devices to the client device may be used including, e.g., auditoryinput (e.g., spoken words), a physical keyboard, mouse, and/or ajoystick. Some embodiments provide various visual feedback to virtualcamera manipulations, such as displaying an animation of possiblevirtual camera manipulations when transitioning from two-dimensional mapviews to three-dimensional map views.

In some embodiments, a client device 1102 a-1102 c implements anavigation system (e.g., turn-by-turn navigation), which may be part ofan integrated mapping and navigation application. A navigation systemprovides directions or route information, which may be displayed to auser. As mentioned above, a client device may receive both map imagedata and route data from the map service 1130. In some embodiments, thenavigation feature of the client device provides real-time route anddirection information based upon location information and routeinformation received from a map service and/or other location system,such as a Global Positioning Satellite (GPS) system. A client device maydisplay map image data that reflects the current location of the clientdevice and update the map image data in real-time. The navigationfeatures may provide auditory or visual directions to follow a certainroute, and some embodiments display map data from the perspective of avirtual camera biased toward the route destination during turn-by-turnnavigation.

The client devices 1102 a-1102 c of some embodiments implement varioustechniques to utilize the received map service data (e.g., optimizedrendering techniques). In some embodiments, a client device locallystores some of the information used to render map data. For instance,client devices may store style sheets with rendering directions forimage data containing style identifiers, common image textures (in orderto decrease the amount of map image data transferred from the mapservice), etc. The client devices of some embodiments may implementvarious techniques to render two-dimensional and three-dimensional mapimage data, including, e.g., generating three-dimensional buildings outof two-dimensional building footprint data; modeling two-dimensional andthree-dimensional map objects to determine the client devicecommunication environment; generating models to determine whether maplabels are seen from a certain virtual camera position; and generatingmodels to smooth transitions between map image data.

In various embodiments, map service 1130 and/or other service(s) 1150are configured to process search requests from any of the clientdevices. Search requests may include but are not limited to queries forbusinesses, addresses, residential locations, points of interest, orsome combination thereof. Map service 1130 and/or other service(s) 1150may be configured to return results related to a variety of parametersincluding but not limited to a location entered into an address bar orother text entry field (including abbreviations and/or other shorthandnotation), a current map view (e.g., user may be viewing one location onthe multifunction device while residing in another location), currentlocation of the user (e.g., in cases where the current map view did notinclude search results), and the current route (if any). In variousembodiments, these parameters may affect the composition of the searchresults (and/or the ordering of the search results) based on differentpriority weightings. In various embodiments, the search results that arereturned may be a subset of results selected based on specific criteriaincluding but not limited to a quantity of times the search result(e.g., a particular point of interest) has been requested, a measure ofquality associated with the search result (e.g., highest user oreditorial review rating), and/or the volume of reviews for the searchresults (e.g., the number of times the search result has been review orrated).

In various embodiments, map service 1130 and/or other service(s) 1150are configured to provide auto-complete search results that aredisplayed on the client device, such as within the mapping application.For instance, auto-complete search results may populate a portion of thescreen as the user enters one or more search keywords on themultifunction device. In some cases, this feature may save the user timeas the desired search result may be displayed before the user enters thefull search query. In various embodiments, the auto complete searchresults may be search results found by the client on the client device(e.g., bookmarks or contacts), search results found elsewhere (e.g.,from the Internet) by map service 1130 and/or other service(s) 1150,and/or some combination thereof. As is the case with commands, any ofthe search queries may be entered by the user via voice or throughtyping. The multifunction device may be configured to display searchresults graphically within any of the map display described herein. Forinstance, a pin or other graphical indicator may specify locations ofsearch results as points of interest. In various embodiments, responsiveto a user selection of one of these points of interest (e.g., a touchselection, such as a tap), the multifunction device is configured todisplay additional information about the selected point of interestincluding but not limited to ratings, reviews or review snippets, hoursof operation, store status (e.g., open for business, permanently closed,etc.), and/or images of a storefront for the point of interest. Invarious embodiments, any of this information may be displayed on agraphical information card that is displayed in response to the user'sselection of the point of interest.

In various embodiments, map service 1130 and/or other service(s) 1150provide one or more feedback mechanisms to receive feedback from clientdevices 1102 a-1102 c. For instance, client devices may provide feedbackon search results to map service 1130 and/or other service(s) 1150(e.g., feedback specifying ratings, reviews, temporary or permanentbusiness closures, errors etc.); this feedback may be used to updateinformation about points of interest in order to provide more accurateor more up-to-date search results in the future. In some embodiments,map service 1130 and/or other service(s) 1150 may provide testinginformation to the client device (e.g., an A/B test) to determine whichsearch results are best. For instance, at random intervals, the clientdevice may receive and present two search results to a user and allowthe user to indicate the best result. The client device may report thetest results to map service 1130 and/or other service(s) 1150 to improvefuture search results based on the chosen testing technique, such as anA/B test technique in which a baseline control sample is compared to avariety of single-variable test samples in order to improve results.

While the invention has been described with reference to numerousspecific details, one of ordinary skill in the art will recognize thatthe invention can be embodied in other specific forms without departingfrom the spirit of the invention. For instance, many of the figuresillustrate various touch gestures (e.g., taps, double taps, swipegestures, press and hold gestures, etc.). However, many of theillustrated operations could be performed via different touch gestures(e.g., a swipe instead of a tap, etc.) or by non-touch input (e.g.,using a cursor controller, a keyboard, a touchpad/trackpad, a near-touchsensitive screen, etc.). In addition, a number of the figuresconceptually illustrate processes. The specific operations of theseprocesses may not be performed in the exact order shown and described.The specific operations may not be performed in one continuous series ofoperations, and different specific operations may be performed indifferent embodiments. Furthermore, the process could be implementedusing several sub-processes, or as part of a larger macro process. Thus,one of ordinary skill in the art would understand that the invention isnot to be limited by the foregoing illustrative details, but rather isto be defined by the appended claims.

What is claimed is:
 1. A method of providing turn-by-turn navigationdirections as a device traverses a physical route, the device having atouch-sensitive display screen, the method comprising: presenting anavigation presentation from a perspective of a virtual camera thattraverses along a virtual route on a map as the device traverses alongthe physical route, the presentation including a first portion of thevirtual route; receiving a touch input on the navigation presentation tolook at a second portion of the virtual route; showing an instruction onthe navigation presentation to perform a maneuver corresponding to thesecond portion; changing the perspective of the virtual camera; andmoving the virtual camera along the virtual route to generate anddisplay renderings of the map at the second portion of the virtualroute.
 2. The method of claim 1, further comprising: displaying, on thenavigation presentation, a navigation banner view including a firstmaneuver banner corresponding to the first portion of the route;displaying the second portion in response to the touch input, whereinthe second portion corresponds to a second maneuver banner; andmaintaining the first maneuver banner on the navigation banner view. 3.The method of claim 1, further comprising: changing the perspective ofthe virtual camera to display the second portion of the route.
 4. Themethod of claim 3, wherein changing the perspective of the virtualcamera further comprises rotating the virtual camera to display thesecond portion of the route, wherein the second portion is larger thanthe first portion.
 5. The method of claim 1, further comprising:determining that a distance between an upcoming maneuver and a currentlocation of the device is less than a threshold distance, wherein theupcoming maneuver corresponds to a third portion of the route;determining that the touch input is currently being received; andmaintaining a display of the second portion of the route on thenavigation presentation in preference to a third portion of the route.6. The method of claim 1, wherein a device representation correspondingto the device is no longer visible within the second portion of theroute.
 7. The method of claim 1, further comprising: computing a firstdistance based on the received touch input; and computing a seconddistance to move the navigation presentation along the route, whereinthe second distance is directly proportional to the first distance. 8.The method of claim 7, wherein the second distance is not directlyproportional to the first distance, further comprising: generating aformulation wherein an increase to the second distance gradually reducesas the first distance increases; and computing the second distance tomove the navigation presentation along the route.
 9. The method of claim1, further comprising: determining a road corresponding to the secondportion of the route; and determining a map label associated with theroad; and displaying the map label in conjunction with the road whiledisplaying the second portion of the route.
 10. A non-transitory machinereadable medium storing a program for providing turn-by-turn navigationdirections as a device traverses a physical route, the device having atouch-sensitive display screen, the program for execution by at leastone processing unit, the program comprising sets of instructions for:presenting a navigation presentation from a perspective of a virtualcamera that traverses along a virtual route on a map as the devicetraverses along the physical route, the presentation including a firstportion of the virtual route; receiving a touch input on the navigationpresentation to look at a second portion of the virtual route; showingan instruction on the navigation presentation to perform a maneuvercorresponding to the second portion; changing the perspective of thevirtual camera; and moving the virtual camera along the virtual route togenerate and display renderings of the map at the second portion of thevirtual route.
 11. The non-transitory machine readable medium of claim10, wherein the program further comprises sets of instructions for:displaying, on the navigation presentation, a navigation banner viewincluding a first maneuver banner corresponding to the first portion ofthe route; displaying the second portion in response to the touch input,wherein the second portion corresponds to a second maneuver banner; andmaintaining the first maneuver banner on the navigation banner view. 12.The non-transitory machine readable medium of claim 10, wherein changingthe perspective of the virtual camera further comprises rotating thevirtual camera to display the second portion of the route, wherein thesecond portion is larger than the first portion.
 13. The non-transitorymachine readable medium of claim 10, wherein the program furthercomprises sets of instructions for: determining that a distance betweenan upcoming maneuver and a current location of the device is less than athreshold distance, wherein the upcoming maneuver corresponds to a thirdportion of the route; determining that the touch input is currentlybeing received; and maintaining a display of the second portion of theroute on the navigation presentation in preference to a third portion ofthe route.
 14. The non-transitory machine readable medium of claim 10,wherein the program further comprises sets of instructions for:determining a road corresponding to the second portion of the route; anddetermining a map label associated with the road; and displaying the maplabel in conjunction with the road while displaying the second portionof the route.
 15. A mobile device comprising: a set of processing unitsfor processing sets of instructions; a non transitory machine readablemedium storing a program, which when executed by at least one processingunit of the mobile device, provides turn-by-turn navigation directionsas a device traverses a physical route, the device having atouch-sensitive display screen, the program comprising sets ofinstructions for: presenting a navigation presentation from aperspective of a virtual camera that traverses along a virtual route ona map as the device traverses along the physical route, the presentationincluding a first portion of the virtual route; receiving a touch inputon the navigation presentation to look at a second portion of thevirtual route; showing an instruction on the navigation presentation toperform a maneuver corresponding to the second portion; changing theperspective of the virtual camera; and moving the virtual camera alongthe virtual route to generate and display renderings of the map at thesecond portion of the virtual route.
 16. The mobile device of claim 15,wherein the program further comprises sets of instructions for:displaying, on the navigation presentation, a navigation banner viewincluding a first maneuver banner corresponding to the first portion ofthe route; displaying the second portion in response to the touch input,wherein the second portion corresponds to a second maneuver banner; andmaintaining the first maneuver banner on the navigation banner view. 17.The mobile device of claim 15, wherein changing the perspective of thevirtual camera further comprises rotating the virtual camera to displaythe second portion of the route, wherein the second portion is largerthan the first portion.
 18. The mobile device of claim 15, wherein theprogram further comprises sets of instructions for: determining that adistance between an upcoming maneuver and a current location of thedevice is less than a threshold distance, wherein the upcoming maneuvercorresponds to a third portion of the mute; determining that the touchinput is currently being received; and maintaining a display of thesecond portion of the route on the navigation presentation in preferenceto a third portion of the route.
 19. The mobile device of claim 15,wherein a device representation corresponding to the device is no longervisible within the second portion of the route.
 20. The mobile device ofclaim 15, wherein the program further comprises sets of instructionsfor: determining a road corresponding to the second portion of theroute; and determining a map label associated with the road; anddisplaying the map label in conjunction with the road while displayingthe second portion of the route.